-
Notifications
You must be signed in to change notification settings - Fork 593
Feat/support az multi parameter #1629
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Feat/support az multi parameter #1629
Conversation
Welcome @Mikey032! |
Hi @Mikey032. Thanks for your PR. I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: Mikey032 The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/ok-to-test |
Hi @dankova22, were you able to review this already? |
@Mikey032: The following test failed, say
Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here. |
Is this a bug fix or adding new feature?
New feature
What is this PR about? / Why do we need it?
Currently, cross-account mounts with dynamic provisioning and without DNS setup, only support mounting a single availability zone, either by providing a specific AZ or by not specifying any and receiving a random one. The AZ multi parameter returns a map of availability zone IDs with their respective mount target IPs to the PV. When combined with the node CSI driver querying the EC2 instance metadata endpoint for its own availability zone, allows it to automatically selects the mount target IP for a pod in the same availability zone.
When used with a multi-AZ EKS deployment, this reduces cross-AZ traffic costs and increases resilience. This does not disrupt the current logic.
What testing is done?
Unit tests have been updated, the logic has been verified on a cluster and EFS file system each in their own VPC and account attached to a transit gateway.